SPARF: Lineup Orders

Note: The lineup program is largely untested. Report problems.

Known bugs:

• Hates whitespace. Trailing, or intial whitespace is bad. internal whitespace should consist of single spaces (not tabs or multi-spaces). This will be the first thing to get fixed.
• Only tells you about the first error instead of all of them
• Minimal error checking for optional arguments after "end"

Format:

start
<pos> <player>
<pos> <player>
 :
 :
<pos> <player>
end

The positions use these exact abbreviations:

Abbr Position

RKM Ruckman
ROV Rover
RKR Ruck-Rover

LFP Left Forward Pocket
FF Full Forward
RFP Right Forward Pocket

LHF Left Half Forward
CHF Centre Half Forward
RHF Right Half Forward

LW Left Wing
C Centre
RW Right Wing

LHB Left Half Back
CHB Centre Half Back
RHB Right Half Back

LBP Left Back Pocket
FB Fullback
RBP Right Back Pocket

IC1 Interchange (substitute)
IC2 Interchange (substitute)
IC3 Interchange (substitute)

Example:

start
RKR Real Great Guy
ROV Swell Fast Guy
RKM Super Spectacular Guy
C Well Rounded Guy
RW Right Footed Guy
LW Left Footed Guy
FF Injury Prone Guy
RFP Fast Guy
LFP Slow Guy
FB Big Guy
LBP Little Guy
RBP Tiny Guy
CHF Miniscule Guy
CHB Huge Guy
IC1 Replacement Guy
IC2 Other Replacement
IC3 Yet_Other Replacement
LHF Another Guy
RHF Super Guy
RHB Penultimate Guy
LHB Fred
end
FCP 8
ORD RKM RKR ROV C CHF FF CHB FB /* proposed */
321 RKM ROV CHF /* proposed */
231 RKR FF /* proposed */

Optional Arguments:

• FCP - Fatigue Cap

No effect on game. Only used when creating lineups for "missed" turns. (fixlineup) No player in the Roster with a Fatigue *higher* than the Fatigue Cap will be used to build a new Lineup. If there are insufficient players to make a new lineup "warm bodies" will be purchased to fill lineup.

• ORD - Substitution Evaluation Order (proposed)

123, 132, 213, 231, 312, 321 - IC order per position. (123 default)

*If adopted* will affect game and fixlineup (see above). At each substitution opportunity the game manager will use the ORD list and the IC order instructions to decide where to put ICs in for injured players. The manager will check positions in ORD list order for injured players. When the manager finds a position with an injured player, it will substitute ICs in the order specified by the IC order instructions. In the example given above, if the RKR FF and C get taken off-field then IC2 becomes RKR, IC1 becomes C and IC3 becomes FF. If that is not clear, then send email to SPARF teamcode yobbo until it becomes clear.

Further explanation by Scott Emery

• 2F and DPM don't do anything anymore.
• DPM has been replaced by FCP.
• 2F has been replaced by ORD, 123, 132, 213, 231, 312, 321. The new stuff allows you to have more control that the old stuff did in addition to handling the complexity of three ICs.

Every time someone is taken off the field or put back on the field, each position on the field is checked for health in a specified order. The first position that needs to be taken off the field gets ICed for first. This continues in this manner until the ICs are used up. What happens then is the simulator's problem.

You can control the order in which the positions are checked by using the ORD line. If you don't use the ORD line, the simulator will check in its default order, which I suspect is LFP, FF, RFP, LHF, CHF, RHF, LW, C RW, LHB, CHB, RHB, LBP, FB, RBP, ROV, RKM, RKR. Mel will have to confirm that about the simulator. If you use the ORD line then the positions that you specify will be dragged to the front of the line in the order given. For example "ORD RKM RKR ROV C" will change the above order to RKM, RKR, ROV, C, LFP, FF, RFP, LHF, CHF, RHF, LW, RW, LHB, CHB, RHB, LBP, FB, RBP. If you are not clear on this, then specify your entire starting team (*not* the ICs) on the ORD line and it will be unambiguous.

You can control the order in which a certain position attempts to take ICs by using the numeric (123, 132, 213, 231, 312, 321) lines. The line is suggestive of the order in which the ICs will be checked for the specified positions. If you don't specify a position on a numeric line then the simulator will check IC1 first, then IC2, then IC3 (as if you put the position on a line starting with 123). One gotcha is that if you accidentally put a position down on two different numeric lines it will take the line specified last in the file as correct, overwriting the earlier specification. The moral is, don't specify a position on two numeric lines and you won't get confused.

Example:

...
end
ORD RKM ROV RKR
132 RKR
312 FB

Suppose the RKR becomes injured and the RKM and FB are already injured. The simulator would start at the top of the ORD list and check the RKM... The RKM is injured and needs a sub. The RKM has not been specified on a numeric line, so it will check IC1 then IC2 then IC3. IC1 is available and is subbed into the RKMs slot. The ROV is checked and is not injured. no subbing occurs. The RKR is checked and needs a sub. The RKR is specified on a 132 line which means that the simulator will check IC1, then IC3 then IC2 in its search for subs. The simulator checks IC1, but that IC has already been subbed into the RKM slot. The simulator checks IC3, which is available and subs it into the RKR field position. The simulator then checks LFP on down to FB, all positions before the FB are healthy and do not need subs. The FB is injured. The FB appears on the numeric line 312. The simulator will check IC3 then IC2 then IC1. It checks IC3, but that IC is presently in the RKR slot. The simulator then checks IC1, but that IC is in the RKM slot, finally the simulator checks IC2... IC2 is available and is put in as FB.